Method and apparatus for ldpc transmission over a channel bonded link

ABSTRACT

A particular overall architecture for transmission over a bonded channel system consisting of two interconnected MoCA (Multimedia over Coax Alliance) 2.0 SoCs (Systems on a Chip) and a method and apparatus for the case of a “bonded” channel network. With a bonded channel network, the data is divided into two segments, the first of which is transported over a primary channel and the second of which is transported over a secondary channel.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of copending U.S. patent application Ser. No. 14/877,598, filed Oct. 7, 2015, which is a continuation of U.S. patent application Ser. No. 14/510,971, filed Oct. 9, 2014, now U.S. Pat. No. 9,184,872, which is a division of U.S. patent application Ser. No. 14/165,005, filed Jan. 27, 2014, now U.S. Pat. No. 8,913,635, which is a continuation of U.S. patent application Ser. No. 13/402,014, filed Feb. 22, 2012, now U.S. Pat. No. 8,638,808, which is a continuation-in-part of U.S. patent application Ser. No. 12/833,827, filed Jul. 9, 2010, now U.S. Pat. No. 8,553,727, which claims the priority benefit of U.S. Provisional Patent Application Ser. No. 61/224,445, filed Jul. 9, 2009. Each of the applications identified above is hereby incorporated herein by reference in its entirety.

TECHNICAL FIELD

The disclosed method and apparatus relates to communications generally, and more particularly, some embodiments relate to communications over a bonded channel between nodes within a network.

BACKGROUND

In many communications applications, it is desirable to send as much information as possible as fast as possible. One way to increase the amount of information that can be sent in a predetermined amount of time is to send the information in parallel (i.e., send information over more than one wire or channel at the same time). However, in some communications systems, such parallel communications require coordination between the channels that are concurrently sending information.

In particular, in a home entertainment network, such as a network that is operated in accordance with the well-known MoCA standard, sending information over different channels requires coordination that makes it difficult to use hardware that is not in close communication.

In a single channel MoCA network, the process of transmitting an aggregate data packet (A-PDU) over the network consists of these steps:

A transmitting node requests a time slot for the transmission;

A Network Controller (NC) grants the request if channel resources are available;

The transmitting and receiving nodes transmit and receive packets at the specified times.

For this process to be successful, both the transmitter and the receiver independently calculate the appropriate LDPC forward error correction code parameters and the number of padding bits to be used.

When trying to coordinate more than one channel acting in concert to transmit information in parallel, coordinating such hardware can be cumbersome and complex. Accordingly, there is a need for a method and apparatus that will allow for relatively easy coordination of hardware that can transmit information over more than one “bonded” channel at the same time.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

The disclosed method and apparatus, in accordance with one or more various embodiments, is described with reference to the following figures. The drawings are provided for purposes of illustration only and merely depict examples of some embodiments of the disclosed method and apparatus. These drawings are provided to facilitate the reader's understanding of the disclosed method and apparatus. They should not be considered to limit the breadth, scope, or applicability of the claimed invention. It should be noted that for clarity and ease of illustration these drawings are not necessarily made to scale.

FIG. 1 is a block diagram illustrating the scheduling of the Allocation Unit (AU) by the NC.

FIG. 2 is a block diagram illustrating the MAP processing by the Transmitting Node.

FIG. 3 is a block diagram illustrating the MAP processing by the Receiving Node.

SUMMARY OF DISCLOSED METHOD AND APPARATUS

Various embodiments of the disclosed method and apparatus for low density parity check (LDPC) transmission over a bonded channel are presented.

According to one embodiment, a particular overall architecture is disclosed for transmission over a bonded channel system consisting of two interconnected MoCA (Multimedia over Coax Alliance) 2.0 SoCs (“Systems on a Chip).

This disclosure provides a method and apparatus for the case of a “bonded” channel network. With a bonded channel network, the data is divided into two segments, the first of which is transported over a primary channel and the second of which is transported over a secondary channel.

DETAILED DESCRIPTION

Derivation of the Reservation Request Parameters

In accordance with the well-known MoCA 2.0 standard for home entertainment communication networks, information is organized into protocol data units. Several of these protocol data units can be aggregated together to form an aggregated protocol data unit (A-PDU). For each A-PDU that a transmitting node has to transmit, a reservation request (RR) information element (IE) is sent to the network controller (NC) requesting a transmission slot for that A-PDU. An IE is defined as optional information that is encoded in a format. The format comprises a “Type”, a “Length” and a “Value”. The Type is a numeric code which indicates the kind of field that this part of the message represents. The Length is the size of the value field. The Value is a variable sized set of bytes which contains data for this part of the message. IEs are used in messages such as MAPs, Reservation Requests, Probe Reports, Pre-admission Discovery Requests and Responses, and Device Discovery messages, each of which are defined by the MoCA 2.0 specification.

In one embodiment of the disclosed method and apparatus, when a transmitting node has an A-PDU to transmit, the A-PDU comprising a particular number of bytes (“M”), the transmitting node calculates the number of symbols (N_(sym)) required to transmit the M bytes of the A-PDU. If both the transmitting and receiving node are capable of operating with channel bonding and the transmission indicates either a unicast profile in channel bonding or a VLPER (very low packet error rate) unicast profile in channel bonding by transmitting a physical layer (PHY) profile value that is equal to 0×12 (i.e., the hexadecimal value equivalent to the binary value “0001 0010”), the number of symbols N_(sym)is calculated as follows:

N_(BAS,1), N_(BAS,2): The number of bits per Orthogonal Frequency Division Multiplexing (OFDM) symbol for the two channels to be used (i.e., the primary and extension channels), respectively;

N_(parity): The number of parity bits per LDPC codeword (same for both channels);

kLDPC_(max,1), kLDPC_(max,2): Maximum LDPC codeword payload sizes from EVM reports for each channel

M_(OH): Bonded channel frame splitting overhead (fixed at 34 Bytes top to cover the worst case)

M_(BAS,i): the (approximate) maximum number of payload bits per OFDM symbol for each channel i.

M_(BAS)=M_(BAS,1)+M_(BAS,2): the maximum payload bits per bonded OFDM symbol

Where

${M_{{BAS},i} = \left\lfloor {N_{{BAS},i} \times \frac{{kLDPC}_{{{ma}\; x},i}}{{kLDPC}_{{{ma}\; x},i} + N_{parity}}} \right\rfloor},{i = 1},2$

The ratio p_(i) of the payload that can be carried by the primary channel with respect to the extension channel is calculated by the transmitting node with 16 bit precision as

The ratio p_(i) of the payload that can be carried by the primary channel with respect to the extension channel is calculated by the transmitting node with 16 bit precision as

${p_{i} = {{{{floor}\left( {2^{16} \times \frac{M_{{BAS},i}}{M_{BAS}}} \right)} \times 2^{- 16}i} = 1}},2$

If ┌p₁(M+M_(OH))┐−18 is a multiple of 4, then the number of bytes to be transmitted in the primary channel is calculated, by the transmitting node, as:

M ₁ =┌p ₁(M+M _(OH))┐

and as:

M ₁=max(M, [p ₁(M+M _(OH))]+4−(([p ₁(M+M _(OH))]−18)mod 4))

in all other cases.

In this last manipulation, we extended the primary channel fragment (minus the MoCA header of 18 bytes) to the nearest 4 byte boundary in order to satisfy the requirement that each fragment is a multiple of 4 bytes. To prevent that extension from making M₁ exceed the total number of bytes M, the above equation caps M₁ to the total number of bytes M. Finally, the transmitting node calculates the payload of the secondary channel as:

M ₂ =M+M _(OH) −M ₁

The minimum number of LDPC codewords needed to transport M_(i) bytes is calculated as:

${B_{{m\; i\; n},i} = {{\left\lceil \frac{M_{i} \times 8}{{kLDPC}_{{{ma}\; x},i}} \right\rceil i} = 1}},2$

and the number of OFDM symbols needed to transmit those codewords is calculated as:

${N_{{SYM},i} = {{\left\lceil \frac{{M_{i} \times 8} + {B_{{m\; i\; n},i} \times {Nparity}}}{B_{{BAS},i}} \right\rceil i} = 1}},2$

Finally, the transmitting node calculates the number of OFDM symbols that need to be reserved as:

) N _(SYM)=max(N _(SYM,1) , N _(SYM,2))

Additionally, the transmitting node calculates a set of optimized forward error correction (FEC) parameters, and includes the number of the FEC padding bytes M_(FECpad) in its RR. These parameters are calculated as follows:

The first step of this calculation includes computing the number of information bytes Imax_(i), i=1,2 that can be transported in the primary and secondary channel in the given N_(SYM) symbols. This is accomplished by application of the following equations:

The minimum number of LDPC codewords is calculated as:

${B_{{m\; i\; n},i} = \left\lfloor \frac{N_{sym} \times N_{{BAS},i}}{{kLDPC}_{{{ma}\; x},i} + {Nparity}} \right\rfloor},{i = 1},2$

Targeted number of LDPC codewords is calculated as:

$B_{{LDPC} \cdot i} = {M_{m\; i\; {n \cdot i}} + \left\{ {{{\begin{matrix} 0 & \begin{matrix} {{{N_{SYM} \times N_{{BAS},i}} - {B_{{m\; i\; n},i} \times \left( {{kLDPC}_{{{ma}\; x},i} + {N\; {parity}}} \right)}} <} \\ {Nparity} \end{matrix} \\ 1 & {otherwise} \end{matrix}\mspace{20mu} B_{{LDPC},i}} = {{{\min \left( {B_{{LDPC},i},N_{sym}} \right)}\mspace{14mu} i} = 1}},2} \right.}$

Target LDPC payload is calculated as:

${{kLDPC}_{{target},i} = {{\left\lceil \frac{N_{sym} \times N_{{BAS},i}}{B_{{LDPC},i}} \right\rceil - {{Nparity}\mspace{14mu} i}} = 1}},2$

Where

-   (kLDPC_(i), nLDPC_(i)) code parameters for all but the last codeword

${kLDPC}_{i} = \left\{ {{{\begin{matrix} {kLDPC}_{{{ma}\; x},i} & {{{if}\mspace{14mu} {kLDPC}_{{target},i}} > {kLDPC}_{{{ma}\; x},i}} \\ {N_{{BAS},i} - {Nparity}} & {{{{if}\mspace{14mu} {kLDPC}_{{target},i}} + {Nparity}} < N_{{BAS},i}} \\ {kLDPC}_{{target},i} & {otherwise} \end{matrix}\mspace{14mu} i} = 1},{{2\mspace{20mu} {nLDPC}_{i}} = {{kLDPC}_{i} + {Nparity}}}} \right.$

and where the number of information bytes is calculated as:

${I\; \max_{i}} = \left\{ {{{\begin{matrix} \left\lfloor {B_{{LDPC},i} \times {k_{{LDPC}_{i}}/8}} \right\rfloor & {{{{if}\mspace{14mu} N_{sym} \times B_{{BAS},i}} - {B_{{LDPC},i} \times {nLDPC}_{i}}} \geq 0} \\ \left\lfloor {\left( {{N_{sym} \times N_{{BAS},i}} - {\times B_{{LDPC},i}}} \right)/8} \right\rfloor & {otherwise} \end{matrix}i} = 1},2} \right.$

-   (kLDPC_(1ast,i),nLDPC_(1ast,i)) code parameters (for i=1,2) are     calculated as follows:

kLDPC_(1ast,i)=8×Imax_(i)−(B_(LDPC,i), −1)×kLDPC_(i),

except if kLDPC_(1ast,i)≦0, in which case B_(LDPC,i) and kLDPC_(1ast,i) are modified from the above values as follows:

B _(LDPC,i) =B _(LDPC,i)−1

kLDPC_(1ast,i) =kLDPC_(1ast,i) +kLDPC_(i)

where B_(LDPC,i) is now the actual number of codewords.

-   nLDPC_(1ast,i) is calculated as:

nLDPC_(1ast,i) =kLDPC_(1ast,i) +Nparity.

In addition to the number of information bytes, Imax_(i), the above equations also compute the FEC parameters (kLDPC_(i), nLDPCD_(i) and (kLDPC_(1ast,i), nLDPC_(1ast,i)).

The required padding is calculated by the transmitting node as:

M _(FEDpad,i) =Imax_(i) −M _(i)

N _(OFDMpad,i)=┌(N _(sym) ×N _(BAS,i)−(_(LDPC,i)−1)×nLDPC_(i) −nLDPC_(last,i))/8┐i=1,2

Notice that in the rare event that one of the two channels is granted one more OFDM symbol than what is strictly necessary to carry M_(i) bytes, the number of FEC padding bytes may exceed the length of a codeword.

The transmitting node includes the summation of the two FEC padding bytes values M_(FECpad,1)+M_(FECpad,2) in the field PARAMETERS of its RR IE. The transmitting node includes the required time slots for transmitting the A-PDU, computed from N_(sym).

Scheduling of the AU by the NC

Once the RR IE is received by the NC, the requested AU (Allocation unit) has to be scheduled. The scheduling algorithm is understood by those of ordinary skill in the art and provided in the MoCA 2.0 standard. If the AU is successfully scheduled, then the NC will grant the time slots requested in the media access plan (MAP). If there is no time available for granting the AU then the NC will ignore the request. If there is only partial time available, the NC grants a number of OFDM symbols N′_(sym)<N_(sym). In this case, the transmission will be fragmented. The NC calculates the number of symbols N″_(sym) that will be required for the second fragment. This calculation is as follows:

The NC follows the calculations used to derive the Reservation Request Parameters (as noted above) for the requested number of symbols N_(sym) and derive the quantities, Imax₁ and Imax₂.

Using these quantities together with the quantity M_(FECpad,1)+M_(FECpad,2) from the RR IE, the NC calculates the total number of bytes by

M=Imax₁ +Imax₂−(M _(FECpad,1) +M _(FECpad,2)).

The NC follows the calculations used to derive the Reservation Request Parameters (as noted above) for the granted number of symbols N′_(sym)<N_(sym) and derives the following quantities Imax′₁+Imax′₂

The NC further calculates the number of padding bytes in the primary and secondary channel of the first fragment to make the fragment a multiple of four bytes M′_(FECpad,1)=Imax′₁ mod 4 and M′_(FECpad,2)=Imax′₂ mod 4, respectively.

Given these quantities, the NC calculates the total number of bytes, M′, transmitted in the first transmission of N′_(sym) symbols as:

M′=Imax′₁ +Imax′₂ −M′ _(FECpad,1) −M′ _(FECpad,2).

The NC also calculates the remaining bytes to be transmitted as: M″=M−M′+M_(OH), adding the extra header overhead bytes for the second fragment.

Then, the NC follows the calculations used to derive the Reservation Request Parameters (as noted above) to derive the required number of symbols N′_(sym) for the second fragment transmission given the number of bytes to be transmitted M″+M_(OH) (including the overhead for splitting the second fragment across the two channels). Further fragmentation of the remaining aggregation unit (AU) of N″_(sym) length is also possible, by repeating this process.

MAP Processing-Transmitting Node

Once the RR is transmitted, the transmitting node awaits reception of the MAP. After the MAP has been received, the transmitting node encodes and transmits the A-PDU in the granted AU using the following parameters:

FEC parameters (kLDPC₁, nLDPC₁) and (kLDPC_(last), 1,nLDPC_(last,1)) for the primary channel and (kLDPC₂,nLDPC₂) and (kLDPC_(last,2), nLDPC_(last,2)) for the secondary channel;

Payload and padding parameters M₁, M_(FECpad,1), N_(OFDMpad,1) for the primary channel and M₂, M_(FECpad,2), N_(OFDMpad,2) for the secondary channel;

Bitloading PHY profile parameters, encryption key parameters etc.

If only a partial grant is received for a given A-PDU, the transmitting node follows the calculations used to calculate the scheduling of the AU by the NC (as noted above) for calculating the first granted fragment FEC padding information M′_(FECpad,1) and payload M′₁=Imax′₁−M′_(FECpad,1) for the primary channel and similarly M′_(FECpad,2) and payload M′₁=Imax′₂−M′_(FECpad,2) for the secondary channel. The MoCA header, aggregation sub-header and FCSs are constructed for the transmission in each channel, and the transmission of the first fragment is scheduled; then the process is repeated for the second (or more) granted fragments.

MAP Processing-Receiving Node

Upon reception of the MAP, the receiving node calculates the number of symbols in the granted AU from the information in the MAP IE. If the number of symbols is equal to the number of symbols requested N_(sym) the receiving node follows the calculations used to derive the Reservation Request Parameters (as noted above) (given the number of symbols N_(sym)) and derives Imax₁, Imax₂.

In addition to the information bytes, Imax₁, this process also computes the FEC parameters (kLDPC_(i), nLDPC_(i)) and (kLDPC_(last,i), nLDPC_(last,i)) that will be needed when the transmission is scheduled.

Once the OFDM symbols are received and the LDPC decoder has decoded the LDPC payload, the receiving Node computes the end point of the data segment on each channel from the information received in the header of each channel segment. All data beyond this point is treated as FEC padding and will be discarded. The two segments across the two channels are re-assembled into a single A-PDU and processing from that point on will proceed as in the single channel case.

If the granted number of symbols is less than the requested N′_(sym)<N_(sym), then the receiving node follows the calculations used to derive the Reservation Request Parameters (as noted above) (given the number of symbols N′_(sym)) and derives Imax′₁, Imax′₂.

In addition to the information bytes Imax′₁, this process also computes the FEC parameters (kLDPC′i, nLDPC′i) and (kLDPC′last,i, nLDPC′last,i) that will be needed when the fragment transmission is scheduled.

Once the OFDM symbols are received and the LDPC decoder has decoded the LDPC payload, the receiving Node SHALL compute the end point of the data segment on each channel from the information received in the header of each channel segment. All data beyond this point is treated as FEC padding and will be discarded. The two segments across the two channels are re-assembled into a single A-PDU fragment. The same process is repeated for the reception of the second fragment and the two fragments are further processed.

While various embodiments of the disclosed method and apparatus have been described above, it should be understood that they have been presented by way of example only, and should not limit the claimed invention. It will be apparent to one of skill in the art how alternative functional, logical or physical partitioning and configurations can be implemented to implement the desired features of the disclosed method and apparatus. Also, a multitude of different constituent module names other than those depicted herein can be applied to the various components and elements disclosed. Additionally, with regard to operational descriptions, the order in which the steps are presented herein shall not mandate that various embodiments be implemented to perform the recited functionality in the same order unless the context dictates otherwise.

Although the disclosed method and apparatus is described above in terms of various embodiments and implementations, it should be understood that the various features, aspects and functionality described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described. Thus, the breadth and scope of the claimed invention should not be limited by any of the above-described embodiments.

Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing: the term “including” should be read as meaning “including, without limitation” or the like; the term “example” is used to provide exemplary instances of the item in discussion, not an exhaustive or limiting list thereof; the terms “a” or “an” should be read as meaning “at least one,” “one or more” or the like; and adjectives such as “conventional,” “traditional,” “normal,” “standard,” “known” and terms of similar meaning should not be construed as limiting the item described to a given time period or to an item available as of a given time, but instead should be read to encompass conventional, traditional, normal, or standard technologies that may be available or known now or at any time in the future Likewise, where this document refers to technologies that would be apparent or known to one of ordinary skill in the art, such technologies encompass those apparent or known to the skilled artisan now or at any time in the future.

A group of items linked with the conjunction “and” should not be read as requiring that each and every one of those items be present in the grouping, but rather should be read as “and/or” unless expressly stated otherwise. Similarly, a group of items linked with the conjunction “or” should not be read as requiring mutual exclusivity among that group, but rather should also be read as “and/or” unless expressly stated otherwise. Furthermore, although items, elements or components of the disclosed method and apparatus may be described or claimed in the singular, the plural is contemplated to be within the scope thereof unless limitation to the singular is explicitly stated.

The presence of broadening words and phrases such as “one or more,” “at least,” “but not limited to” or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent. The use of the term “module” does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. Indeed, any or all of the various components of a module, whether control logic or other components, can be combined in a single package or separately maintained and can further be distributed in multiple groupings or packages or across multiple locations.

As will become apparent to one of ordinary skill in the art after reading this document, the disclosed embodiments and their various alternatives can be implemented without confinement to the examples presented. 

1-2. (canceled)
 3. A multimedia over coaxial cable communication network comprising: a transmitting node; and a network coordinator (NC) node, wherein: the transmitting node is operable to, at least, transmit a resource reservation request to the NC node, the resource reservation request comprising a first field indicating a requested bandwidth for transmitting a data unit on a plurality of bonded channels; the NC node is operable to, at least: receive the resource reservation request from the transmitting node; and if an amount of available bandwidth is less than the requested bandwidth, then: assign an allocation of bandwidth to the second node that is less than the requested bandwidth, wherein the allocation of bandwidth is for communicating a first fragment of the data unit on the plurality of bonded channels; and transmit a Media Access Plan (MAP) message indicating the allocation of bandwidth to the transmitting node; and the transmitting node is operable to, at least: receive the MAP message from the NC; and if the allocated bandwidth is less than the requested bandwidth, then: fragment the data unit into a plurality of fragmented data units; and for each fragmented data unit of the plurality of fragmented data units: calculate, for each of the bonded channels, a respective FEC padding value and a respective payload parameter; and encode and transmit the fragmented data unit on the bonded channels using the respective FEC padding values and the respective payload parameters.
 4. The communication network of claim 3, wherein the NC node is operable to, if the amount of available bandwidth is less than the requested bandwidth, then determine a remaining amount of bandwidth for communicating a remainder of the data unit on the plurality of bonded channels.
 5. The communication network of claim 4, wherein the NC node is operable to determine the remaining amount of bandwidth by, at least in part, operating to determine a remaining amount of bytes, including additional overhead bytes related to splitting the data unit across multiple channels and across multiple time periods.
 6. The communication network of claim 3, wherein the resource reservation request comprises a second field comprising a padding byte summation value comprising a summation of, for each bonded channel of the plurality of bonded channels, a respective number of forward error correction (FEC) padding bytes for transmitting a respective portion of the data unit on said each bonded channel.
 7. A network node for use in a multimedia over coaxial cable communication network comprising a network coordinator (NC) node, the network node operable to at least: transmit a resource reservation request to the NC node, the resource reservation request comprising: a first field indicating a requested bandwidth for transmitting a data unit on a plurality of bonded channels; and a second field comprising a padding byte summation value comprising a summation of, for each bonded channel of the plurality of bonded channels, a respective number of forward error correction (FEC) padding bytes for transmitting a respective portion of the data unit on said each bonded channel; receive a message from the NC node, the message indicating an allocated bandwidth for transmitting the data unit on the plurality of bonded channels; and if the allocated bandwidth is less than the requested bandwidth, then: fragment the data unit into a plurality of fragmented data units; and for each fragmented data unit of the plurality of fragmented data units: calculate, for each of the bonded channels, a respective FEC padding value and a respective payload parameter; and encode and transmit the fragmented data unit on the bonded channels using the respective FEC padding value and the respective payload parameter.
 8. The network node of claim 7, wherein the network node is operable to, if the allocated bandwidth is at least the requested bandwidth, then encode and transmit the data unit on the bonded channels using, for each of the bonded channels, a respective FEC parameter value, a respective payload parameter value, and a respective padding parameter value.
 9. The network node of claim 7, wherein the first field indicating a requested bandwidth comprises information specifying a number of time slots.
 10. The network node of claim 7, wherein the message received from the NC node comprises a Media Access Plan (MAP) message.
 11. The network node of claim 7, wherein the plurality of bonded channels comprises only a primary channel and a secondary channel.
 12. The network node of claim 7, wherein the network node is operable to request the bandwidth for transmitting the data unit on the plurality of bonded channels only when a destination node for the data unit is capable of receiving the data unit over the plurality of bonded channels.
 13. The network node of claim 7, wherein the network node is operable to request the bandwidth for transmitting the data unit on the plurality of bonded channels only when the data unit is to be unicast.
 14. The network node of claim 7, wherein the communication network is a premises-based coaxial cable network.
 15. A network coordinator (NC) node for use in a multimedia over coaxial cable communication network comprising a second node, the NC node operable to at least: receive a resource reservation request from the second node, the resource reservation request comprising: a first field indicating a requested bandwidth for transmitting a data unit on a plurality of bonded channels; and a second field comprising a padding byte summation value comprising a summation of, for each bonded channel of the plurality of bonded channels, a respective number of forward error correction (FEC) padding bytes for transmitting a respective portion of the data unit on said each bonded channel; if an amount of available bandwidth is less than the requested bandwidth, then: assign an allocation of bandwidth to the second node that is less than the requested bandwidth, wherein the allocation of bandwidth is for communicating a first fragment of the data unit on the plurality of bonded channels; transmit a message indicating the allocation of bandwidth to the second node; and determine a remaining amount of bandwidth for communicating a remainder of the data unit on the plurality of bonded channels.
 16. The network coordinator node of claim 15, wherein the NC node is operable to determine the remaining amount of bandwidth by, at least in part, operating to determine a remaining amount of bytes, including additional overhead byes related to splitting the data unit.
 17. The network coordinator node of claim 16, wherein the additional overhead bytes comprise first additional overhead bytes related to splitting the data unit across two channels and second overhead bytes related to splitting the data unit across multiple time periods.
 18. The network coordinator node of claim 16, wherein the NC node is operable to determine the remaining amount of bandwidth by, at least in part, operating further to determine a number of symbols necessary to transmit the remaining amount of bytes.
 19. The network coordinator node of claim 15, wherein the NC node is operable to, if there is no available bandwidth to allocate to the second node for transmitting the data unit, then ignore the received resource reservation request.
 20. The network coordinator node of claim 15, wherein the NC node is operable to, if there is enough available bandwidth to allocate the requested bandwidth to the second node, then allocate the requested bandwidth to the second node.
 21. The network coordinator node of claim 15, wherein the NC node is operable to allocate the requested bandwidth for transmitting the data unit on the plurality of bonded channels only when the data unit is to be unicast.
 22. The network coordinator node of claim 15, wherein the transmitted message indicating the allocation of bandwidth to the second node comprises a Media Allocation Plan (MAP) message. 